Add stateless closure cache - #23203
Closed
iluuu1994 wants to merge 2 commits into
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
https://wiki.php.net/rfc/closure-optimizations#stateless_closure_caching
Extracted from #19941. Sadly, @DanielEScherzer discovered an edge-case I did not consider:
https://3v4l.org/uovSF#v8.5.9
Here, the internal function
array_map()can perform instance calls with just a named closure. Same with['Foo', 'instanceCall']. That's quite esoteric, but this behavior should first be deprecated and removed before assuming it isn't being used.So, for the time being, let's merge only the latter half of the RFC. Code bases with
staticproperly annotated will still get the full performance benefit.